Method and apparatus and non-transitory computer-readable storage medium for debugging solid-state disk (ssd) device

ABSTRACT

The invention relates to a method, an apparatus and a non-transitory computer-readable storage medium for debugging a solid-state disk (SSD) device. The method is performed by a processing unit of a single-board personal computer (PC) when loading and executing a function of a runtime library, to include: receiving a request to drive a General-Purpose Input/Output (GPIO) interface (I/F), which includes a parameter required for completing a Joint Test Action Group (JTAG) command; issuing a first hardware instruction to the GPIO I/F to set a register corresponding to a GPIO test data input (TDI) pin according to the parameter carried in the request for emulating to issue the JTAG command to a solid-state disk (SSD) device, wherein the single-board PC is coupled to the SSD device through the GPIO I/F; issuing a second hardware instruction to the GPIO I/F to read a value of the register corresponding to the GPIO TDI pin; and replying with a completion message in response to the request.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. Provisional Application Ser. No. 63/215,732, filed on Jun, 28, 2021; and Patent Application No. 202111133825.7, filed in China on Sep. 27, 2021; the entirety of which is incorporated herein by reference for all purposes.

BACKGROUND

The disclosure generally relates to storage devices and, more particularly, to a method, an apparatus, and a non-transitory computer-readable storage medium for debugging a solid-state disk (SSD) device.

The problems encountered by using the commercially available in-circuit emulator (ICE) to collect firmware (FW) statuses during the operations of SSD products include: Firstly, the ICE cannot be fully controlled to meet all application environments. For example, the ICE device when being stopped performs regular operations, such as stopping the central processing unit (CPU) in the SSD product, etc., which causes a host to be unable to access to data in the SSL) product later. Secondly, the response of ICE is very slow when the FW reads hardware (FM) registers after an address changing is required. For example, the debugging engineer wants to access to the HW registers to know the NAND flash statuses when the FW is stuck. Thirdly, the ICE is expensive and the debugging cost needs to be reduced. Thus, it is desirable to have a method, an apparatus, and a non-transitory computer-readable storage medium for debugging an SSD device to address or alleviate the aforementioned problems.

SUMMARY

In an aspect of the invention, an embodiment introduces a method for debugging a solid-state disk (SSD) device, performed by a processing unit of a single-board personal computer (PC) when loading and executing a function of a runtime library, to include: receiving a request to drive a General-Purpose Input/Output (GPIO) interface (I/F), which includes a parameter required for completing a Joint Test Action Group (JTAG) command; issuing a first hardware instruction to the GPIO I/F to set a register corresponding to a GPIO test data input (TDI) pin according to the parameter carried in the request for emulating to issue the JTAG command to a solid-state disk (SSD) device, wherein the single-board PC is coupled to the SSD device through the GPIO issuing a second hardware instruction to the GPIO I/F to read a value of the register corresponding to the GPIO TDI pin; and replying with a completion message in response to the request.

In another aspect of the invention, an embodiment introduces a non-transitory computer-readable storage medium to include computer code of a function of a runtime library for debugging SSD devices. The computer code when being loaded and executed by a processing unit of a single-board PC to practice the aforementioned method.

In still another aspect of the invention, an embodiment introduces an apparatus for debugging SSD devices to include: a GPIO I/F, coupled to the SSD device; and a processing unit, coupled to the GPIO I/F. The processing unit when loading and executing a function of a runtime library is arranged operably to: receive a request to drive the GPIO I/F, which includes a parameter required for completing a JTAG command; issue a first hardware instruction to the GPIO PT to set a register corresponding to a GPIO TDI pin according to the parameter carried in the request for simulating to issue the JTAG command to the SSD device; issue a second hardware instruction to the GPIO I/F to read a value of the register corresponding to the GPIO TDI pin; and reply with a completion message in response to the request.

Both the foregoing general description and the following detailed description are examples and explanatory only, and are not restrictive of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is the block diagram of debugging system according to an embodiment of the invention.

FIG. 2 is the system architecture of Raspberry Pi according to an embodiment of the invention.

FIG. 3 is a schematic diagram illustrating Argonaut Reduced Instruction Set Computer Core (ARC) auxiliary register set according to an embodiment of the invention.

FIG. 4 is a schematic diagram illustrating bit assignments for Argonaut RISC Machine (ARM) auxiliary control register and secondary auxiliary control register according to an embodiment of the invention.

FIG. 5 is a flowchart illustrating a method for debugging solid-state disk (SSD) devices, performed by a debugging application, according to an embodiment of the invention.

FIG. 6 is a schematic diagram showing pins of General-Purpose Input/Output (GPIO) interface (I/F) in Raspberry Pi according to an embodiment of the invention.

FIG. 7 is a schematic diagram showing Joint Test Action Group (JTAG) 20-pin to 10-pin in a JTAG connection device according to an embodiment of the invention.

FIG. 8 is the pin-out diagram for GPIO LT in a Raspberry Pi according to an embodiment of the invention.

FIG. 9 is a flowchart illustrating a method for debugging SSD devices, performed by a function in a runtime library, according to an embodiment of the invention.

DETAILED DESCRIPTION

Reference is made in detail to embodiments of the invention, which are illustrated in the accompanying drawings. The same reference numbers may be used throughout the drawings to refer to the same or like parts, components, or operations.

The present invention will be described with respect to particular embodiments and with reference to certain drawings, but the invention is not limited thereto and is only limited by the claims. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including,” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Use of ordinal terms such as “first”, “second”, “third”, etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one claim element having a certain name from another element having the same name (but for use of the ordinal term) to distinguish the claim elements.

It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected” or “directly coupled” to another element, there are no intervening elements present. Other words used to describe the relationship between elements should be interpreted in a like fashion (e.g., “between” versus “directly between,” “adjacent” versus “directly adjacent.” etc.)

Refer to FIG. 1 illustrating a block diagram for a debugging system. The debugging system 10 includes the debugging device 120, the personal computer (PC) 130, the Joint Test Action Group (JTAG) connection device 140, the Universal Asynchronous Receiver/Transmitter (UART) recording device 150 and the power source 160. The solid-state disk (SSD) device 120 is provided on the PC 130. The debugging device 110 draws power from the power source 160 and supplies power to the personal computer 130, the JTAG connection device 140 and the UART recording device 150. The PC 130 supplies power to the SSD device 120.

The SSD 120 device is a device to be debugged, and at least includes a flash controller 121 and a flash module 128. The flash module 128 provides huge storage space typically in hundred Gigabytes (GBs), or even several Terabytes (TBs), for storing a wide range of user data, such as high-resolution images, video files, etc. The flash controller 121 includes the host interface (I/F) 129 for connecting to the PC 130 to draw power. The host I/F 129 and the device I/F 132 of the PC 130 may communicate with each other by Universal Serial Bus (USB), Advanced Technology Attachment (ATA), Serial Advanced Technology Attachment (SATA), Peripheral Component interconnect Express (PCI-E), Universal Flash Storage (UFS), Embedded Multi-Media Card (eMMC) protocol, or others. The flash controller 121 includes the processing unit 125, which communicates with the host I/F 121, the auxiliary (AUX) register 122, the JTAG I/F 123, the UART I/F 124, the memory 126 and the device I/F 127 each other through bus architecture for transmitting and receiving such as commands, control signals, messages, data, etc. The processing unit 125 may be implemented in numerous ways, such as with general-purpose hardware (e.g., a microcontroller unit, a single processor, multiple processors or graphics processing units capable of parallel computations, or others) that is programmed using firmware and/or software instructions to access to the auxiliary register 122 and the memory 125 for reading and storing such as variables, data tables, data, messages, etc. during the execution. For example, the processing unit 125 may be Argonaut Reduced instruction Set Computer (RISC) Core tor ARC for short), Argonaut RISC Machine or ARM for short), or others. The content stored in the auxiliary register 122 and the memory 126 are important references (or clues) for debugging. In some embodiments, the memory 126 may be a static random access memory (SRAM). In alternative embodiments, the memory 126 may be a SRAM and a dynamic random access memory (DRAM). The device I/F 127 and the flash module 128 may communicate with each other by a Double Data Rate (DDR) protocol, such as Open NAND Flash Interface (ONFI), DDR Toggle, or others, for reading, programming or erasing data. The SSD device 120 connects to the JTAG connection device 140 through JTAG I/F, and to the UART recording device 150 through UART I/F.

The auxiliary register 122 may conform to ARC, ARM, or other specifications. For example, FIG. 3 shows a summary of the auxiliary register set taken from pages 45-46 of ARCCompact™ Instruction Set Architecture: Programmer's Reference, April 2008. Part A in FIG. 4 shows the bit assignments of auxiliary control register excerpted from page 4-41 of Cortex™-R5 and Cortex-R5F revision:rlpl, Technical Reference Manual published in 2010-2011. Part B in FIG. 4 shows the bit assignments of secondary auxiliary control register excerpted from page 4-45 of Cortex™-R5 and Cortex-R5F revision:rlpl, Technical Reference Manual published in 2010-2011.

An embodiment of the invention utilizes the debugging device 110, the JTAG connection device 140 and the UART recording device 150 to replace the commercially available in-circuit emulator (ICE), so as to avoid the technical problems encountered during a debugging of hardware and software in the SSD device 120 by using the ICE. Moreover, the dubbing cost using the debugging device 110, the JTAG connection device 140 and the UART recording device 150 is lower than that using the ICE.

The debugging device 110, the kernel of the debugging system 10, includes the Raspberry Pi 112 and the JTAG add-on board 114. The raspberry Pi 112 is a single-board computer based on Linux operating system (OS). The debugging application runs on the Raspberry Pi 112, and the firmware to be debugged runs on the SSD device 120, The Raspberry Pi 112 when executing the debugging application fees the power source 160 into the PC 130 through the General-Purpose Input/Output (GPIO) I/F to start the PC 130, so that the SSD device 120 is also started up. Next, it is determined whether the PC 130 is successfully started according to the signal for driving the light-emitting diode (LED). Since the JTAG I/F can be driven by common IO signals, the Raspberry Pi 112 when executing the debugging application simulates the JTAG behavior through the built-in GPIO I/F to obtain the required information from the SSD device 120, and the access speed may be faster than 4 Mbps. The communications protocol of JTAG may refer to the IEEE Standard Test Access Port and Boundary-Scan Architecture admitted on Jun. 14, 2001. The Raspberry Pi 112 when executing the debugging application forces the SSD device 120 to enter the read-only memory (ROM) mode through the built-in GPIO I/F and the JTAG connection device 140. When the SSD device 120 enters the ROM mode, the processing unit 125 loads program code from the ROM (not shown in FIG. 1 ) and executes the program code to perform operations for booting up the system, such as a wide range of hardware tests, etc. The Raspberry Pi 112 when executing the debugging application collects such as UART data, signals, messages, etc. through the built-in USB I/F and the UART recording device 150. An engineer may manipulate the Raspberry Pi 112 to debug the hardware of the SSD device 120 and/or the firmware executed in the SSD device 120. For example, the Raspberry Pi 112 may be equipped with the Wi-Fi or the Bluetooth module, and the engineer may establish a remote connection with the Raspberry Pi 112 through the Wi-Fi or the Bluetooth module thereof to control the debugging device 110.

Refer to FIG. 2 illustrating the system architecture of the Raspberry Pi 112. The processing unit 210 may be an ARM-based processor, and when executing the instructions of the debugging application, performs the functions described below. The tool developer may use Python to write the instructions of debugging application. The Raspberry Pi 112 may include different types of buses that can be used in combination: Advanced High-performance Bus/Advanced System Bus (AHB/ASB) 222; and Advanced Peripheral Bus (APB) 224. The AHB/ASB 222 and the APB 224 are connected by the bridge 220. AHB/ASB 222 satisfies the requirements of high-speed bandwidth between the processing unit 210 through the memory controller 230 and the SRAM 232, the DRAM 234 or the flash memory 236. APB 224 is suitable for peripheral devices with low power consumption, such as the GPIO I/F 260, the USB I/F 270, the Wi-Fi. module 280, the Bluetooth module 290, etc. The processing unit 210 may simulate the JTAG behavior through the GPIO I/F 260, and receive such as UART data, signals, messages, etc., through the USB I/F 270, The processing unit 210 may receive a debugging request from a remote device through the Wi-Fi module 280 or the Bluetooth module 290, and load and execute the debugging application in response.

An embodiment of the invention introduces a method for debugging SSD, which is performed by the processing unit 210 when loading and executing program codes of the debugging application. Referring to FIG, 5, the detailed description is as follows:

Step S510: The JTAG command is simulated to issue through the GPIO I/F 260 for reading the identifier (ID) of the processing unit 125 of the flash controller 121 in the SSD device 120, such as ARC ID, ARM ID, etc. For example, the ID of the processing unit 125 is read from the designated address of the AUX register 122 in the SSD device 120. In some embodiments, ARC ID is recorded in the 0^(th) to 7^(th) bits of the 4^(th) double-byte “ARCVER[7:0]” in FIG. 3 .

Step S520: It is determined whether the ID is correct. If the ID is correct, then the process proceeds to step S530. Otherwise, the process proceeds to step S525. This step can be used to confirm if the debugging device 110 is properly connected to the SSD device 120. If the processing unit 210 cannot read the ID associated with the processing unit 125 of the flash controller 121 from the SSD device 120, then it means that the debugging device 110 is not properly connected to the SSD device 120.

Step S525: The debugging application replies with an error message to the upper layer that started the debugging application. The upper layer may drive a display to show the error message, or store the error message in the flash memory 236 to inform an engineer that an error has occurred during the debugging.

Step S530: The JTAG command is simulated to issue through the GPIO a 260 for stopping the running of the processing unit 125 of the flash controller 121 in the SSD device 120. For example, the value of designated address of the AUX register 122 in the SSD device is modified to stop the processing unit 125. In some embodiments, the 1^(st) bit of the 5^(th) double-byte “FH” in FIG. 3 is set to “1” to stop the processing unit 125.

Step S540: The JTAG command is simulated to issue through the GPIO I/F 260 for forcing the SSD device 120 to exit the sleep mode. For example, the value of designated address of the AUX register 122 in the SSD device is modified to exit the sleep mode. In some embodiments, the 23^(th) bit of the 5^(th) double-byte “ZZ” in FIG. 3 is set to “0” to force the SSD device 120 to exit the sleep mode.

Step S550: The JTAG command is simulated to issue through the GPIO I/F 260 for reading the in-system programming (ISP) code from the SSD device 120. For example, the ISP code may be stored in the designated address of the flash module 128, and the debugging application simulates the JTAG command for reading a predefined length of data (that is, the ISP code) from the designated address of the flash module 128. The ISP code contains a variety of processes for executing host commands issued by a host, or performing background operations, such as the garbage collection (GC), the wear leveling (WL), the read reclaim, the read refresh processes, and the like. The host commands are commands that are defined by a standard-setting organization, such as Universal Flash Storage (UFS), Non-Volatile Memory Express (NVMe), Open-channel SSD, etc.

Step S560: A checksum for the ISP code is calculated. The debugging application may use predetermined algorithm to calculate the checksum, such as MD5, SHA1, SHA256, SHA512, etc.

Step S570: It is determined whether the checksum is correct. If the checksum is correct, then the process proceeds to step S580. Otherwise, the process proceeds to step S525. In some embodiments, since the manufacturer of the flash controller 121 in the SSD device 120 may provide different versions of ISP code in response to different types of NAND flash memory, the flash memory 236 in the Raspberry Pi 112 may store several checksums corresponding to different versions of ISP codes, respectively, in advance. The debugging application may compare the checksum generated in step S560 with the checksums stored in the flash memory 236. If the checksum generated in step S560 matches any of the checksums stored in the flash memory 236, then the generated checksum is correct (also, the ISP code executed in the flash controller 121 of the SSD device 120 can be recognized as the specific version of ISP code). Otherwise, the generated checksum is incorrect (that is, the ISP code executed in the flash controller 121 of the SSD device 120 is incorrect, or unable to recognize). This step is used not only to judge if the generated checksum is correct, but also to know which version of ISP code that is currently executed in the flash controller 121. It is noted that different versions of ISP codes have different logics for allocating memory space to store such as variables, data tables, data to be programmed into the flash module 128, data has been read from the flash module 128 etc. in execution. That is, the debugging application needs to know the memory allocation logic first, and then dumps required data from the designated addresses of the memory 126 (including SRAM, DRAM, or both) in the SSD device 120 according to the memory allocation logic.

Step S580: The JTAG command is simulated to issue through the GPIO I/F 260 for reading data from the SRAM in the SSD device 120. For example, firmware data generated during boot-up or during normal operation is stored at specified addresses in the SRAM. The debugging application may issue multiple JTAG commands to the SSD device 120, and each JTAG command requests to read the specified length of data (i.e. firmware data) from the specified address of the SRAM. In some embodiments, the flash memory 236 in the Raspberry Pi 112 may store a document having multiple records. Each record includes information about a start address and a length. The debugging application may issue a JTAG command to the SSD device 120 for reading the specified length of data from the specified address of the SRAM according to each record in the document.

Step S590: In some embodiments with DRAM in the memory 126, the JTAG command is simulated to issue through the GPIO I/F 260 for reading data from the DRAM in the SSD device 120. For example, firmware data generated during boot-up or during normal operation is stored at specified addresses in the DRAM. The debugging application may issue multiple JTAG commands to the SSD device 120, and each JTAG command requests to read the specified length of data (i.e. firmware data) from the specified address of the DRAM. In some embodiments, the flash memory 236 in the Raspberry Pi 112 may store a document having multiple records. Each record includes information about a start address and a length. The debugging application may issue a JTAG command to the SSD device 120 for reading the specified length of data from the specified address of the DRAM according to each record in the document.

Step S595: The JTAG command is simulated to issue through the GPIO I/F 260 for resuming the processing unit 125 of the flash controller 121 in the SSD device 120. For example, the value of designated address of the AUX register 122 in the SSD device 120 is modified to resume the processing unit 125. In some embodiments, the 1^(st) bit of the 5^(th) double-byte “FH” in FIG. 3 is set to “0” to resume the processing unit 125.

The following shows exemplary pseudo code of the debugging application: read aux_register bit[7:0] of DWORD 4 as arc_arm_ID //Obtain ARC/ARM ID

If arc_arm_ID == False  return error EndIf write “1” into aux_register bit[1] of DWORD 5 //Stop SSD CPU write “0” into aux_register bit[23] of DWORD 5 //Leave sleep mode read memory_ISP //Dump ISP Code //Compare MD5 Calculate memory_ISP as MD5_ISP If MD5_ ISP != MD5_Target  return error EndIf //Dump destination memory For readLine(target_memory_list) != endOfFile  read memory_Target  save as memory_Target.bin EndFor //Dump DRAM If DRAM==True  For readLine(dram_memory_list) != endOfFile   read memory_dram   save as memory_dram.bin  Endfor EndIf //Resume CPU If freeRun==True  write “0” into aux_register bit[1] of DWORD 5 EndIf

The method for debugging SSD devices implemented by the debugging application as described above would be more flexible than the ICE to solve the problems encountered during the debugging. For example, when the firmware of the SSD device is stuck, the hardware register would be quickly accessed to obtain the statuses of the NAND flash memory.

Refer to FIGS. 1 and 2 . The UART recording device 150 includes the USB I/F, the UART I/F, the controller, and the memory. The USB of the UART recording device 150 is connected to the USB I/F of the Raspberry Pi 112, and the UART I/F of the UART recording device 150 is connected to the UART I/F 124 of the SSD device 120. The UART recording device 150 receives log information including such as data, message, signals, etc. from the SSD device 120 through its UART I/F, and sends the log information to the Raspberry Pi 112 through its USB I/F. The UART recording device 150 includes a non-volatile storage unit for storing the log information received from the SSD device 120. Each port on the USB I/F is connected to the designated port on the UART I/F through a level shifter. The level shifter is used to translate an input signal from the voltage domain of USB I/F to the voltage domain of UART I/F, or translate an input signal from the voltage domain of UART I/F to the voltage domain of USB I/F.

With references made to FIG. 6 , the Raspberry Pi 112 may be connected to the JTAG add-on board 114 through 40 pins of the GPIO I/F 260. The JTAG add-on board 114 is capable of transmitting signals between the Raspberry Pi 112 and the JTAG connection device 140 and transmitting signals between the Raspberry Pi 112 and the PC 130. The JTAG add-on board 114 includes the GPIO I/F and the type-C I/F, the GPIO I/F is connected to the Raspberry Pi 112 and the PC 130, and the type-C I/F is connected to the JTAG connection device 140. Each port on the GPIO I/F is connected to the designated port on the type-C I/F through a level shifter. The level shifter is used to translate an input signal from the voltage domain of GPIO I/F to the voltage domain of type-C I/F, or translate an input signal from the voltage domain of type-C I/F to the voltage domain of GPIO I/F.

The JTAG connection device 140 can be regarded as a JTAG adaptor, such as 20-pin to 10-pin, 20-pin to 8-pin, etc., and is capable of transmitting the JTAG commands emulated by the Raspberry Pi 112, and data from the JTAG add-on board 114 to the SSD device 120, and transmitting the data output from the SSD device 120 to the Raspberry Pi 112 through the JTAG add-on board 114. The JTAG connection device 140 includes the type-C I/F, the JTAG I/F, the controller and the memory. The type-C I/F of JTAG connection device 140 may be connected to the type-C I/F of the JTAG add-on board 114, and the JTAG I/F of the JTAG connection device 140 may be connected to the JTAG I/F 123 of the SSD device 120. It is noted that, since the SSD device 120 needs to be tested in a test chamber under a high temperature environment, the JTAG connection device 140 is independent from the JTAG add-on board 114, instead of integrating the JTAG connection device 140 into the JTAG add-on board 114, so that the SSD device 120 and the JTAG connection device 140 can be placed in the test chamber together for debugging operations. Refer to FIG. 7 illustrating the exemplary JTAG 20-pin to 10-pin adaptor including the 20-pin connector 710 for connecting the JTAG add-on board 114, and the 10-pin connector 730 for connecting to the JTAG I/F 123, For example, the 9^(th) pin of the connector 710 is used to feed in the test clock (TCLK) signal from the JTAG add-on board 114, and the 4^(th) pin of the connector 730 is used to output the clock signal to the JTAG I/F 123, The 7^(th) pin of the connector 710 is used to input the test mode select input (TMS) signal from the JTAG add-on board 114, and the 2^(nd) pin of the connector 730 is used to output the TMS signal to the JTAG I/F 123. The 5^(th) pin of the connector 710 is used to input the test data input (TDI) signal from the JTAG add-on board 114, and the 8^(th) pin of the connector 730 is used to output the TIM signal to the JTAG I/F 123. The 13^(th) pin of the connector 730 is used to input the test data output (TDO) signal from the JTAG I/F 123, and the 6^(th) pin of the connector 710 is used to output the TDO signal to the JTAG add-on board 114. The 10^(th) pin of the connector 710 is used to input the test reset input (TRST) signal from the JTAG add-on board 114, and the 3^(rd) pin of the connector 730 is used to output the TRST signal to the JTAG I/F 123. Each pin of the connector 710 is connected to the designated pin of the connector 730 through a level shifter. The level shifter is used to translate an input signal from the voltage domain of type-C I/F to the voltage domain of JTAG I/F, or translate an input signal from the voltage domain of JTAG I/F to the voltage domain of type-C I/F.

Three power relays may be disposed on the JTAG add-on board 114, which are connected to the power source. Refer to FIG. 8 illustrating the pin-out diagram for the exemplary GPIO I/F 260. The pins GPIO12, GPIO18 and GPIO23 are respectively used to control three power relays disposed on the JTAG add-on board 114 for feeding in the power source 160 to the PC 130. The pin GPIO17 is connected to the signal line for driving an LED in the PC 130 and is used to detect if the PC 130 starts successfully. The pin GPIO16 is connected to the designated pin of the SSD device 120 for directing the SSD device 120 to enter the ROM mode. The pin GPIO22 is connected to the designated pin of the SATA I/F in the SSD device 120 for directing the SSD device 120 to enter or exit the sleep mode. It is noted that the sleep mode instructed through the SATA I/F cuts off power to most of the components in the SSD device 120 (including the processing unit 125) to save power. In other words, when the sleep mode is entered through the SATA I/F, the processing unit 125 in the SSD device 120 does not perform any operation. The sleep mode that is exited in response to the JTAG command issued by the debugging application, as described above, is different from the sleep mode that is entered through the SATA I/F. The pins GPIO11, GPIO5, GRIO6, GPIO13, GPIO19 and GPIO26 are connected to the JTAG I/F 123 in the SSD device 120 through the JTAG add-on board 114 and the JTAG connection device 140, and are used for the processing unit 210 in the Raspberry Pi 112 when executing the debugging application to simulate the JTAG behavior for issuing the JTAG commands to the SSD device 120, so that the ISP code and the firmware data are obtained from the SSD device 120. For example, the pin GPIO5 is used to send the JTAG TDI signal to the SSD device 120 and the GPIO6 is used to receive the JTAG TDO signal from the SSD device 120. For simulation details of JTAG behavior, refer to IEEE Standard Test Access Port and Boundary-Scan Architecture admitted on Jun. 14, 2001.

Refer to FIG. 2 . The Raspberry Pi 112 is a low-cost PC and therefore does not implement the low latency peripheral port (LLPP) technology, which uses a dedicated path to access the GPIO I/F. When the debugging application in the upper layer accesses to the content of the AUX register 122 or the memory 126 in the SSD device 120 by issuing a JTAG command through the GPIO I/F, the GPIO driver in the lower layer issues a hardware instruction with relevant parameters to the GPIO 260 through AHB/ASB 222 and the APB 224 in sequence for writing (or setting) a value to the register corresponding to the designated pin in the GPIO I/F 260 to complete the specified simulation of JTAG command. However, due to hardware limitations, some hardware instructions may be delayed to arrive at the APB 224. When two hardware instructions for writing to the same register in the GPIO I/F 260 arrive at the APB controller in a very short time interval, the APB controller may mistakenly judge them as incorrect instructions and discard one of them from executing, so that such as certain portions of ISP codes, firmware data, etc. cannot be read back from the SSD device 120.

To address the aforementioned problems, in an embodiment of the invention, the function in the runtime library is modified, which is called by the debugging application to execute for driving the GPIO I/F 260 to complete operations including, for example, the issuance of JTAG commands to read the ID of the processing unit 125 of the flash controller 121 in the SSD device 120, stop the processing unit 125 of the flash controller 121 in the SSD device 120, force the SSD device to exit the sleep mode, read ISP codes stored in the flash module 128 of the SSD device 120, read data from SRAM, DRAM of the SSD device 120, and so on. The runtime library is a collection of built-in functions used by a compiler to implement a programming language to provide a special computer program library that is supported during execution of the programming language. Refer to FIG. 9 , the detailed description is as follows:

Step S910: A request to drive the GPIO I/F is received from the debugging application, which includes one or more relevant parameters for completing a specific JTAG command, For example, corresponding to step S510 in FIG. 5 , refer to FIG. 3 , the parameter of the request includes information for setting the 1^(st) bit of the 5^(th) double-byte in the AUX register 122 to “1”. In correspondence to step S540 in FIG. 5 , refer to FIG. 3 , the parameter of the request includes information for setting the 23^(th) bit of the 5^(th) double-byte in the AUX register 122 to “0”. In correspondence to step S550 in FIG. 5 , the parameter of the request includes information for reading the specified length of data from the specified address of the flash module 128. In correspondence to step S580 in FIG. 5 , the parameter of the request includes information for reading the specified length of data from the specified address of the SRAM. In correspondence to step S590 in FIG. 5 , the parameter of the request includes information for reading the specified length of data from the specified address of the DRAM.

Step S930: A hardware instruction is issued to the GPIO I/F 260 to set the register corresponding to the GPIO TDI pin for simulating the designated JTAG command according to the parameters carried in the request.

Step S950: A hardware instruction is issued to the GPIO PF 260 to read the register value corresponding to the GPIO TDI pin. Due to the operation of this step, one hardware instruction for reading the register value corresponding to the GPIO TDI pin is inserted between two hardware instructions for setting the register corresponding to the GPIO TDI pin, which are generated for two requests. It would prevent the APB controller from mistakenly judging two hardware instructions for setting the register corresponding to the GPIO TDI pin, which are arrived successively in a very short time interval, as incorrect hardware instructions. It is to be understood that this step may be modified to be executed between steps S910 and S930, and the invention should not be limited thereto.

Step S970: A completion message for the driving of GPIO I/F 260 is replied to the debugging application.

The processing unit 210 of the Raspberry Pi 112 may periodically executes another function of runtime library for driving the GPIO I/F 260 to read the register value corresponding to the GPIO TDO pin. The read values are execution outcomes for the JTAG commands that were simulated to issue through the GPIO TDI pin, which are generated by SSD device 120 and may include such as a message indicating a success or a failure of setting to the AUX register 122, the ISP codes read from the flash module 28, firmware data read from the SRAM or DRAM, etc.

Some or all of the aforementioned embodiments of the method of the invention may be implemented in a computer program such as a driver for a dedicated hardware, a firmware program, a software program, or others. Other types of programs may also be suitable, as previously explained. Since the implementation of the various embodiments of the present invention into a computer program can be achieved by the skilled person using his routine skills, such an implementation will not be discussed for reasons of brevity. The computer program implementing some or more embodiments of the method of the present invention may be stored on a suitable computer-readable data carrier such as a DVD, CD-ROM, USB stick, a hard disk, which may be located in a network server accessible via a network such as the Internet, or any other suitable carrier.

Although the embodiment has been described as having specific elements in FIGS. 1 and 2 , it should be noted that additional elements may be included to achieve better performance without departing from the spirit of the invention. Each element of FIGS. 1 and 2 is composed of various circuits and arranged operably to perform the aforementioned operations. While the process flows described in FIGS. 5 and 9 include a number of operations that appear to occur in a specific order, it should be apparent that these processes can include more or fewer operations, which can be executed serially or in parallel (e.g., using parallel processors or a multi-threading environment).

While the invention has been described by way of example and in terms of the preferred embodiments, it should be understood that the invention is not limited to the disclosed embodiments. On the contrary, it is intended to cover various modifications and similar arrangements (as would be apparent to those skilled in the art). Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements. 

What is claimed is:
 1. A method for debugging a solid-state disk (SSD) device, performed by a processing unit of a single-board personal computer (PC) when loading and executing a function of a runtime library, the method comprising: receiving a request to drive a General-Purpose Input/Output (GPIO) interface (I/F), which includes a parameter required for completing a Joint Test Action Group (JTAG) command; issuing a first hardware instruction to the GPIO I/F to set a register corresponding to a GPIO test data input (TDI) pin according to the parameter carried in the request for emulating to issue the JTAG command to the SSD device, wherein the single-board PC is coupled to the SSD device through the GPIO I/F; issuing a second hardware instruction to the GPIO I/F to read a value of the register corresponding to the GPIO TDI pin; and replying with a completion message in response to the request.
 2. The method of claim 1, wherein a signal transmitted on the GPIO TDI pin conforms to a specification of JTAG.
 3. The method of claim 1, wherein the runtime library is a collection of built-in function used by a compiler to implement a programming language.
 4. The method of claim 1, wherein the JTAG command is used to read an identifier of a processing unit of a flash controller in the SSD device.
 5. The method of claim 1, wherein the JTAG command is used to stop a processing unit of a flash controller in the SSD device.
 6. The method of claim 1, wherein the JTAG command is used to force the SSD device to exit a sleep mode.
 7. The method of claim 1, wherein the JTAG command is used to read in-system programming (ISP) code stored in a flash module of the SSD device.
 8. The method of claim 1, wherein the JTAG command is used to read data from a designated location of a static random access memory in the SSD device.
 9. The method of claim 1, wherein the JTAG command is used to read data from a designated location of a dynamic random access memory in the SSD device.
 10. A non-transitory computer-readable storage medium for debugging a solid-state disk (SSD) device when executed by a processing unit of a single-board personal computer, the non-transitory computer-readable storage medium comprising debugging program code of a function of a runtime library to: receive a request to drive a General-Purpose Input/Output (GPIO) interface (I/F), which includes a parameter required for completing a Joint Test Action Group (JTAG) command; issue a first hardware instruction to the GPIO I/F to set a register corresponding to a GPIO test data input (TDI) pin according to the parameter carried in the request for simulating to issue the JTAG command to the SSD device, wherein the single-board PC is coupled to the SSD device through the GPIO I/F; issue a second hardware instruction to the GPIO I/F to read a value of the register corresponding to the GPIO TDI pin; and reply with a completion message in response to the request.
 11. The non-transitory computer-readable storage medium of claim 10, wherein the single-board PC is a Raspberry Pi based on Linux operating system.
 12. The non-transitory computer-readable storage medium of claim 10, wherein a signal transmitted on the GPIO TDI pin conforms to a specification of JTAG.
 13. The non-transitory computer-readable storage medium of claim 10, wherein the runtime library is a collection of built-in function used by a compiler to implement a programming language.
 14. The non-transitory computer-readable storage medium of claim 10, wherein the JTAG command is used to read data from a designated location of a static random access memory in the SSD device.
 15. The non-transitory computer-readable storage medium of claim 10, wherein the JTAG command is used to read data from a designated location of a dynamic random access memory in the SSD device.
 16. An apparatus for debugging a solid-state disk (SSD) device, installed in a single-board personal computer (PC), comprising: a General-Purpose Input/Output (GPIO) interface (I/F), coupled to the SSD device; and a processing unit, coupled to the GPIO I/F, when loading and executing a function of a runtime library, arranged operably to: receive a request to drive the GPIO I/F, which includes a parameter required for completing a Joint Test Action Group (JTAG) command; issue a first hardware instruction to the GPIO I/F to set a register corresponding to a GPIO test data input (TDI) pin according to the parameter carried in the request for simulating to issue the JTAG command to the SSD device; issue a second hardware instruction to the GPIO I/F to read a value of the register corresponding to the GPIO TDI pin; and reply with a completion message in response to the request.
 17. The apparatus of claim 16, wherein a signal transmitted on the GPIO TDI pin conforms to a specification of JTAG.
 18. The apparatus of claim 16, wherein the runtime library is a collection of built-in function used by a compiler to implement a programming language.
 19. The apparatus of claim 16, wherein the JTAG command is used to read data from a designated location of a static random access memory in the SSD device.
 20. The apparatus of claim 16, wherein the JTAG command is used to read data from a designated location of a dynamic random access memory in the SSD device. 